.START:
.AUTHOR: mikebon
.PRODUCT: B_VBASIC
.TITLE: New MSCOMM control available 
.VERSION(S): 2.00 3.00
.OPERATING SYSTEM(S): WINDOWS 
.SECURITY: ENDUSER
.REFERENCE: BugList3.00 Update3.00
.ARTICLE TEXT:

Summary:

A new version of the  MSCOMM control has been made available in LIB 1 of the 
MSBASIC forum on CompuServe.  This control fixes a problem where the OnComm 
event will not fire when communicating with some 14.4 baud modems.

\* MSINTERNAL
\* This file is also available on \\MAINE\PRODUPDT!VB\CONTROLS called 
\* MSCOMM.VBX.

More Information:

The date,time, size and version number of the MSCOMM.VBX file that 
shipped with Visual Basic 3.0 is:

  Date: 28-APR-1993
  Time: 12:00 a.m.
  Size: 34304
  Version: 2.0.9000.7

The date, time, size and version number of the updated MSCOMM.VBX file  
is as follows:

  Date: 12-MAY-1993
  Time: 12:21 p.m.
  Size: 34816
  Version: 2.1.0.1

When using the MSCOMM.VBX provided with Visual Basic version 2.0 or 
3.0 to communicate with a 14.4 baud modem, the OnComm event may not 
fire.  The revised version of the MSCOMM.VBX control available on 
CompuServe fixes this problem by introducing a new Notification 
property.  Since the problem relates to using Windows 3.1 event driven 
communications, this new property allows you to use Windows 3.0 
polling techniques instead.

The Nofication property is not available at design-time, but you can 
get and set its property value at run-time.  It's default value of 0 
specifies that the control should use Windows 3.0 polling techniques 
and a value of 1 specifies that Windows 3.1 event driven 
communications should be used.  However, it is only recommended that 
you set the property value to 1 if you are using the MSCOMM control to 
communicate with a modem whose baud rate is lower than 14.4 baud.

Another change that was made is that the default property setting for 
the Interval property was changed from 1000 to 55.

To install the new control, copy the updated version into the 
WINDOWS\SYSTEM directory on your computer.  Also check to make sure 
that no other copies of MSCOMM.VBX exist on your system.  If you find 
an older version of the MSCOMM.VBX file, you should delete it or 
rename it.

Additional reference words: 2.00 3.00
.END: